-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Merge master to release/3.0.1xx for preview5 #3162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
wli3
merged 64 commits into
release/3.0.1xx
from
merge-master-to-release/3.0.1xx-for-preview5
Apr 22, 2019
Merged
Merge master to release/3.0.1xx for preview5 #3162
wli3
merged 64 commits into
release/3.0.1xx
from
merge-master-to-release/3.0.1xx-for-preview5
Apr 22, 2019
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…utputGroup Adding NetCorePublishItemsOutputGroup to support VS installer project scenarios
Update branding to preview5
Fix various issues in generated RegFree COM manifest
Merge release/3.0.1xx to master
Adding PublishItemsOutputGroup to support VS installer projects
* Switching to Jobs from Phases for YAML and also switch to new pools.
This aligns with current 3.0 templates, and no longer generates warnings
Update stage 0
This commit fixes the ResolvePackageAssets task to escape the output item specs. This allows assets in packages to contain characters that might get unescaped by MSBuild. Fixes #3069.
This lets you restore once and then build for separate RIDs without re-restoring
* Update dependencies from https://github.com/dotnet/arcade build 20190407.1 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19207.1 - Microsoft.DotNet.SignTool - 1.0.0-beta.19207.1 * Update dependencies from https://github.com/dotnet/arcade build 20190409.1 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19209.1 - Microsoft.DotNet.SignTool - 1.0.0-beta.19209.1 * Update dependencies from https://github.com/dotnet/arcade build 20190409.2 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19209.2 - Microsoft.DotNet.SignTool - 1.0.0-beta.19209.2 * Update dependencies from https://github.com/dotnet/arcade build 20190410.7 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19210.7 - Microsoft.DotNet.SignTool - 1.0.0-beta.19210.7
* Update dependencies from https://github.com/dotnet/arcade build 20190415.12 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19215.12 - Microsoft.DotNet.SignTool - 1.0.0-beta.19215.12 * Update dependencies from https://github.com/dotnet/arcade build 20190417.1 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19217.1 - Microsoft.DotNet.SignTool - 1.0.0-beta.19217.1
* Changing crossgen commands to use response files. Changing /Platform_Assemblies_Paths to a set of /r arguments Using resolved files list as assembly references to crossgen (temp hack until issue #3110 is fixed)
…rted scenarios (#3123) * Changes to emit a failure message when enabling ReadyToRun in unsupported scenarios
…418.1 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19218.1 - Microsoft.DotNet.SignTool - 1.0.0-beta.19218.1
Allow disabling apphost
…Symbols, PublishReadyToRunExclude) (#3134) Simplify R2R creation logic: No need to split ResolvedFilesToPublish into PublishAlways and PreserveNewest lists.
…72d-8045a9b6c89a [master] Update dependencies from dotnet/arcade
Update NuGet
…rence Don't include base FrameworkReferences when creating NuGet packages
…418.4 (#3150) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19218.4 - Microsoft.DotNet.SignTool - 1.0.0-beta.19218.4
This change implements support for publishing apps to a [single file](https://github.com/dotnet/designs/blob/master/accepted/single-file/design.md). * ``dotnet publish /p:PublishSingleFile=true`` causes the contents of the "original" publish directory to a single file in the actual publish directory * Files marked with the meta-data ``<ExcludeFromSingleFile>false<ExcludeFromSingleFile>`` are left in the publish directory unbundled. This includes PDB files by default * PDB files can be bundled into the single file by setting ``/p:IncludeSymbolsInSingleFile=true`` Publishing to a single file requires publishing wrt a RID using an apphost, because the generated file is the platform-specific AppHost executable with embedded dependencies.
update stage 0 to 3.0.100-preview5-011481
Switch to new deps file generation mode by default
* Add ILLink targets and tests * Enable and test deps file trimming Deps file trimming doesn't work on ProjectReferences, so this changes the referenced test project to be a PackageReference. We also disable use of the build dependency file when linking, as the publish dependency file needs to be generated based on what the linker decided to remove. * Support old deps generation logic * Update property names and respond to PR feedback The current public-facing linker properties are now: - PublishTrimmed - TrimmerRootDescriptors The IL transform extension point has been named ILTransformForPublish, to make it clear that it only runs on publish. This also enables incremental build for project file changes, and lets the linker run on projects targeting .NETStandard. * Respond to PR feedback - Ensure trailing slash in linker output directory - Disable old deps file generation logic - Don't support netstandard - ExtraLinkerArgs -> _ExtraTrimmerArgs - Remove ILTransformForPublish extension point * Remove left-over ILTransformForPublishDependsOn property
Merge release/3.0.1xx to master 0419
…418.7 (#3160) - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19218.7 - Microsoft.DotNet.SignTool - 1.0.0-beta.19218.7
peterhuene
approved these changes
Apr 22, 2019
wli3
pushed a commit
that referenced
this pull request
Feb 7, 2020
…build 20191010.9 (#3162) - Microsoft.NET.Sdk.Razor - 5.0.0-alpha1.19510.9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.